Job.fastUpdateNextBuildNumber
#9019
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Vlatombe
approved these changes
Mar 8, 2024
timja
approved these changes
Mar 9, 2024
comment-ops-bot
bot
added
the
ready-for-merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduces a minimal beta API that has been used successfully in CloudBees CI to reload a
Job.nextBuildNumberfrom disk. The existingupdateNextBuildNumberis not well suited to this purpose because it forces loading of the last build and also saves the value back to disk, noticeably increasing disk I/O when called frequently on a slower filesystem.Testing done
Integration tests exist in CloudBees CI.
Proposed changelog entries
Before the changes are marked as
ready-for-merge:Maintainer checklist